-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "Make PROC_MACRO_DERIVE_RESOLUTION_FALLBACK a hard error" #107133
Revert "Make PROC_MACRO_DERIVE_RESOLUTION_FALLBACK a hard error" #107133
Conversation
This reverts commit 7d82cad. I am doing this to buy us some time with respect to issue rust-lang#106337 w.r.t. the 1.67 release.
r? @cjgillot (rustbot has picked a reviewer for you, use r? to override) |
beta-nominating, checking with @wesleywiser or @Mark-Simulacrum to see about trying to get this in before the 1.67-beta is uplifted to stable. @rustbot label: beta-nominated |
@bors r+ p=1 |
I don't think that we should revert this, or at least it should be re-landed on the next or next+1 release. |
…mulacrum [beta] backport * Don't wf-check non-local RPITs rust-lang#107038 * Revert "Make PROC_MACRO_DERIVE_RESOLUTION_FALLBACK a hard error" rust-lang#107133 * bump bootstrap 1.66.1 r? `@Mark-Simulacrum`
☀️ Test successful - checks-actions |
Finished benchmarking commit (85da15c): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. |
Obviously I'm in favor of the revert, but I mostly agree with the sentiment of @petrochenkov 's statements. I don't think the lang team has spent very much time at all thinking about #64079, and that there are other points in the solution space that should be considered. I am thinking/hoping we will re-land the hard-error-update sometime in the next 12 to 18 weeks, which I suppose is a slightly longer schedule than what @petrochenkov had proposed. |
This reverts commit 7d82cad aka PR #84022
I am doing this to buy us some time with respect to issue #106337 w.r.t. the 1.67 release.